Release 10.1A: OpenEdge Development:
Progress Dynamics Advanced Development

Creating a new Field Edit manager

This section contains an example of how to design, build, and register a new Field Edit Manager.

The Field Edit Manager supports the definition of special kinds of editing and validation for fields in the application’s database. It also supports the visualization of these characteristics in the client user interface. For example, the developer can define fields that are mandatory, independent of the Progress schema definitions, provide a visual cue for those mandatory fields in the viewers in the application’s maintenance windows, and then ensure that those fields have all been entered before an update is returned to the server. You can define a field as requiring uppercase or lowercase letters only, and you can adjust the screen value for the field accordingly before updated values are returned to the server. This example illustrates a number of ways in which you can extend the framework, including:

Adding a new table to the Repository
Defining the manager itself
Registering the new manager
Accessing the manager from SDOs
Accessing the manager from viewers
Invoking the field edits from an SDO
Testing the new manager